V2X Network Assisted Side-link Configuration and Data Transmission

ABSTRACT

Apparatuses, systems, and methods for a user equipment device (UE) to perform methods for network assisted side-link resource configuration for unicast and/or multi-cast/groupcast communications in V2X networks. A UE may, after establishing an RRC connection with a base station, transmit, to the base station, V2X connection information. The V2X connection information may include a V2X identifier associated with the UE and a V2X identifier associated with a target UE. The UE may receive, from the base station, a side-link configuration for data transmission with the target UE. The side-link configuration may include a resource allocation defined in time and frequency (e.g., a transmit/receive pool). The UE may communicate with the target UE using the resource allocation included in the side-link configuration.

PRIORITY DATA

This application is a continuation of U.S. patent application Ser. No.16/782,414, titled “V2X Network Assisted Side-link Configuration andData Transmission”, filed Feb. 5, 2020, which claims benefit of priorityto Chinese Application No. 201910112790.5, titled “V2X Network AssistedSide-link Configuration and Data Transmission”, filed Feb. 13, 2019,which is hereby incorporated by reference in its entirety as thoughfully and completely set forth herein.

The claims in the instant application are different than those of theparent application or other related applications. The Applicanttherefore rescinds any disclaimer of claim scope made in the parentapplication or any predecessor application in relation to the instantapplication. The Examiner is therefore advised that any such previousdisclaimer and the cited references that it was made to avoid, may needto be revisited. Further, any disclaimer made in the instant applicationshould not be read into or against the parent application or otherrelated applications.

FIELD

The present application relates to wireless devices, and moreparticularly to apparatus, systems, and methods for a wireless device toperform a variety of cellular communication techniques.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. In recentyears, wireless devices such as smart phones and tablet computers havebecome increasingly sophisticated. In addition to supporting telephonecalls, many mobile devices now provide access to the internet, email,text messaging, and navigation using the global positioning system(GPS), and are capable of operating sophisticated applications thatutilize these functionalities. Additionally, there exist numerousdifferent wireless communication technologies and standards. Someexamples of wireless communication standards include GSM, UMTS(associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE,LTE Advanced (LTE-A), HSPA, 3GPP2 CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD,eHRPD), IEEE 802.11 (WLAN or Wi-Fi), BLUETOOTH™, etc.

The ever-increasing number of features and functionality introduced inwireless communication devices also creates a continuous need forimprovement in both wireless communications and in wirelesscommunication devices. To increase coverage and better serve theincreasing demand and range of envisioned uses of wirelesscommunication, in addition to the communication standards mentionedabove, there are further wireless communication technologies underdevelopment, including fifth generation (5G) new radio (NR)communication. Accordingly, improvements in the field in support of suchdevelopment and design are desired.

SUMMARY

Embodiments relate to apparatuses, systems, and methods to performnetwork assisted side-link resource configuration for unicast and/ormulti-cast/groupcast communications in V2X (vehicle to everything)networks.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tocellular phones, tablet computers, wearable computing devices, portablemedia players, and any of various other computing devices.

In some embodiments, a user equipment device (UE) may perform a methodfor network assisted side-link resource configuration. The UE mayestablish a radio resource control (RRC) connection with a base stationand transmit, to the base station, V2X connection information. The V2Xconnection information may include a first V2X identifier associatedwith the UE and a second V2X identifier associated with a target UE(e.g., an intended side-link communication partner). The UE may receive,from the base station, a side-link configuration for data transmissionwith the target UE. The side-link configuration may include a resourceallocation defined in time and frequency (e.g., a transmit/receivepool). The UE may communicate with the target UE using the resourceallocation included in the side-link configuration. In some embodiments,the V2X information may also include at least one of a traffic qualityof service requirement, a traffic pattern requirement, and/or, a V2Xcapability associated with the UE. In some embodiments the side-linkconfiguration may also include at least one of layer two resource blocksand/or a layer one configuration.

In some embodiments, as part of a network assisted side-link resourceconfiguration, a UE may receive, from a base station, a paging messageassociated with a V2X connection request from a source UE. In responseto the paging message, the UE may establish, with the base station, anRRC connection and receive, from the base station, a side-linkconfiguration for data transmission with the source UE. The side-linkconfiguration may include a resource allocation defined in time andfrequency (e.g., a transmit/receive pool). The UE may communicate withthe source UE using the resource allocation included in the side-linkconfiguration.

In some embodiments, a base station may perform a method for networkassisted side-link resource configuration. The base station may receive,from a UE served by the base station, V2X information, including a firstV2X identifier associated with the UE. In addition, the base station mayreceive, from the UE, a V2X connection request. The V2X connectionrequest may include the first V2X identifier and a second V2X identifierassociated with a target UE (e.g., an intended side-link communicationpartner). The base station may transmit, to a neighboring base stationserving the target UE, a V2X UE pair request. The V2X UE pair requestmay include a side-link configuration for data transmissions between theUE and the target UE. The side-link configuration may include a resourceallocation defined in time and frequency (e.g., a transmit/receivepool). The base station may receive, from the neighboring base station,a confirmation of the V2X UE pairing and transmit, to the UE, theside-link configuration.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various embodiments isconsidered in conjunction with the following drawings, in which:

FIG. 1A illustrates an example wireless communication system accordingto some embodiments.

FIG. 1B illustrates an example of a base station (BS) and an accesspoint in communication with a user equipment (UE) device according tosome embodiments.

FIG. 2 illustrates an example simplified block diagram of a WLAN AccessPoint (AP), according to some embodiments.

FIG. 3 illustrates an example block diagram of a UE according to someembodiments.

FIG. 4 illustrates an example block diagram of a BS according to someembodiments.

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some embodiments.

FIG. 6A illustrates an example of connections between an EPC network, anLTE base station (eNB), and a 5G NR base station (gNB).

FIG. 6B illustrates an example of a protocol stack for an eNB and a gNB.

FIG. 7A illustrates an example of a 5G network architecture thatincorporates both 3GPP (e.g., cellular) and non-3GPP (e.g.,non-cellular) access to the 5G CN, according to some embodiments.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments.

FIG. 8 illustrates an example of a baseband processor architecture for aUE, according to some embodiments.

FIG. 9 illustrates an example of a vehicle-to-everything network.

FIGS. 10-12 illustrate block diagrams of examples of signaling fornetwork assisted side-link configuration and setup, according to someembodiments.

FIG. 13 illustrates a block diagram of an example of signaling forrelease of a network assisted side-link transmission configuration,according to some embodiments.

FIG. 14 illustrates a block diagram of an example of signaling for UEhandover during a network assisted side-link transmission, according tosome embodiments.

FIG. 15 illustrates a block diagram of an example of signaling for UEre-establishment after a radio link failure during a network assistedside-link transmission, according to some embodiments.

FIG. 16 illustrates a block diagram of an example of signaling for UEre-establishment failure after a radio link failure during a networkassisted side-link transmission, according to some embodiments.

FIG. 17 illustrates a block diagram of an example of signaling fornetwork assisted side-link configuration and setup failure, according tosome embodiments.

FIG. 18 illustrates a block diagram of an example of signaling fornetwork assisted recovery from a side-link failure, according to someembodiments.

FIG. 19 illustrates a block diagram of an example of signaling fornetwork assisted side-link data transmission, according to someembodiments.

FIG. 20 illustrates a block diagram of an example of signaling fornetwork assisted side-link data transmission with SDAP duplication,according to some embodiments.

FIG. 21 illustrates a block diagram of an example of signaling fornetwork assisted side-link data transmission with PDCP duplication,according to some embodiments.

FIG. 22 illustrates a block diagram of another example of signaling fornetwork assisted side-link data transmission, according to someembodiments.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION Terms

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random-access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems or devices that are mobile or portable and that perform wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, PlayStation Portable™ Gameboy Advance™,iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication.

Wireless Device—any of various types of computer systems or devices thatperform wireless communications. A wireless device can be portable (ormobile) or may be stationary or fixed at a certain location. A UE is anexample of a wireless device.

Communication Device—any of various types of computer systems or devicesthat perform communications, where the communications can be wired orwireless. A communication device can be portable (or mobile) or may bestationary or fixed at a certain location. A wireless device is anexample of a communication device. A UE is another example of acommunication device.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—refers to various elements or combinations ofelements that are capable of performing a function in a device, such asa user equipment or a cellular network device. Processing elements mayinclude, for example: processors and associated memory, portions orcircuits of individual processor cores, entire processor cores,processor arrays, circuits such as an ASIC (Application SpecificIntegrated Circuit), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Uu interface—refers to an over the air interface between a wirelessdevice (such as a UE) and a base station (such as an eNB or a gNB). A Uuinterface may be used by a wireless device to transmit data on an uplinkto a base station and receive data on a downlink from a base station.

PC5 interface—refers to an over the air interface between wirelessdevices (such as a pair of UEs). A PC5 interface may be used by awireless device to transmit data on a side-link to another wirelessdevice or to receive data on a side-link from another wireless device.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thus,the term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some embodiments, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

Concurrent—refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency may be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Configured to—Various components may be described as “configured to”perform a task or tasks. In such contexts, “configured to” is a broadrecitation generally meaning “having structure that” performs the taskor tasks during operation. As such, the component can be configured toperform the task even when the component is not currently performingthat task (e.g., a set of electrical conductors may be configured toelectrically connect a module to another module, even when the twomodules are not connected). In some contexts, “configured to” may be abroad recitation of structure generally meaning “having circuitry that”performs the task or tasks during operation. As such, the component canbe configured to perform the task even when the component is notcurrently on. In general, the circuitry that forms the structurecorresponding to “configured to” may include hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1A and 1B—Communication Systems

FIG. 1A illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102Ais implemented in the context of 5G NR, it may alternately be referredto as gNodeB′ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1 , each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some embodiments, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someembodiments, a gNB may be connected to a legacy evolved packet core(EPC) network and/or to a NR core (NRC) network. In addition, a gNB cellmay include one or more transmission and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 1B illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102 and an accesspoint 112, according to some embodiments. The UE 106 may be a devicewith both cellular communication capability and non-cellularcommunication capability (e.g., Bluetooth, Wi-Fi, and so forth) such asa mobile phone, a hand-held device, a computer or a tablet, or virtuallyany type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD), LTE/LTE-Advanced, or 5G NRusing a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NRusing the single shared radio. The shared radio may couple to a singleantenna, or may couple to multiple antennas (e.g., for MIMO) forperforming wireless communications. In general, a radio may include anycombination of a baseband processor, analog RF signal processingcircuitry (e.g., including filters, mixers, oscillators, amplifiers,etc.), or digital processing circuitry (e.g., for digital modulation aswell as other digital processing). Similarly, the radio may implementone or more receive and transmit chains using the aforementionedhardware. For example, the UE 106 may share one or more parts of areceive and/or transmit chain between multiple wireless communicationtechnologies, such as those discussed above.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 5G NR (or LTE or 1×RTT or LTE or GSM), and separate radios forcommunicating using each of Wi-Fi and Bluetooth. Other configurationsare also possible.

FIG. 2—Access Point Block Diagram

FIG. 2 illustrates an exemplary block diagram of an access point (AP)112. It is noted that the block diagram of the AP of FIG. 2 is only oneexample of a possible system. As shown, the AP 112 may includeprocessor(s) 204 which may execute program instructions for the AP 112.The processor(s) 204 may also be coupled (directly or indirectly) tomemory management unit (MMU) 240, which may be configured to receiveaddresses from the processor(s) 204 and to translate those addresses tolocations in memory (e.g., memory 260 and read only memory (ROM) 250) orto other circuits or devices.

The AP 112 may include at least one network port 270. The network port270 may be configured to couple to a wired network and provide aplurality of devices, such as UEs 106, access to the Internet. Forexample, the network port 270 (or an additional network port) may beconfigured to couple to a local network, such as a home network or anenterprise network. For example, port 270 may be an Ethernet port. Thelocal network may provide connectivity to additional networks, such asthe Internet.

The AP 112 may include at least one antenna 234, which may be configuredto operate as a wireless transceiver and may be further configured tocommunicate with UE 106 via wireless communication circuitry 230. Theantenna 234 communicates with the wireless communication circuitry 230via communication chain 232. Communication chain 232 may include one ormore receive chains, one or more transmit chains or both. The wirelesscommunication circuitry 230 may be configured to communicate via Wi-Fior WLAN, e.g., 802.11. The wireless communication circuitry 230 mayalso, or alternatively, be configured to communicate via various otherwireless communication technologies, including, but not limited to, 5GNR, Long-Term Evolution (LTE), LTE Advanced (LTE-A), Global System forMobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000,etc., for example when the AP is co-located with a base station in caseof a small cell, or in other instances when it may be desirable for theAP 112 to communicate via various different wireless communicationtechnologies.

In some embodiments, as further described below, an AP 112 may beconfigured to implement methods for performing network assistedside-link resource configuration for unicast and/or multi-cast/groupcastcommunications in V2X (vehicle to everything) networks, e.g., as furtherdescribed herein.

FIG. 3—Block Diagram of a UE

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some embodiments. It is notedthat the block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to embodiments,communication device 106 may be a user equipment (UE) device, a mobiledevice or mobile station, a wireless device or wireless station, adesktop computer or computing device, a mobile computing device (e.g., alaptop, notebook, or portable computing device), a tablet and/or acombination of devices, among other devices. As shown, the communicationdevice 106 may include a set of components 300 configured to performcore functions. For example, this set of components may be implementedas a system on chip (SOC), which may include portions for variouspurposes. Alternatively, this set of components 300 may be implementedas separate components or groups of components for the various purposes.The set of components 300 may be coupled (e.g., communicatively;directly or indirectly) to various other circuits of the communicationdevice 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some embodiments, communicationdevice 106 may include wired communication circuitry (not shown), suchas a network interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively; directly or indirectly. dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someembodiments, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be dedicated to a first RAT, e.g.,LTE, and may be in communication with a dedicated receive chain and atransmit chain shared with an additional radio, e.g., a second radiothat may be dedicated to a second RAT, e.g., 5G NR, and may be incommunication with a dedicated receive chain and the shared transmitchain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short range wireless communication circuitry 229,cellular communication circuitry 330, connector I/F 320, and/or display360. The MMU 340 may be configured to perform memory protection and pagetable translation or set up. In some embodiments, the MMU 340 may beincluded as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may be configured to perform methods fordefining and using a resource map for semi-persistent resourcereservations/scheduling for unicast and/or groupcast communications inV2X (vehicle to everything) networks, e.g., as further described herein.

As described herein, the communication device 106 may include hardwareand software components for implementing the above features for acommunication device 106 to communicate a scheduling profile for powersavings to a network. The processor 302 of the communication device 106may be configured to implement part or all of the features describedherein, e.g., by executing program instructions stored on a memorymedium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processor 302 may be configured as aprogrammable hardware element, such as an FPGA (Field Programmable GateArray), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processor 302 of the communicationdevice 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may be configured toimplement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort-range wireless communication circuitry 329 may each include one ormore processing elements. In other words, one or more processingelements may be included in cellular communication circuitry 330 and,similarly, one or more processing elements may be included in shortrange wireless communication circuitry 329. Thus, cellular communicationcircuitry 330 may include one or more integrated circuits (ICs) that areconfigured to perform the functions of cellular communication circuitry330. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of cellular communication circuitry 230. Similarly, theshort-range wireless communication circuitry 329 may include one or moreICs that are configured to perform the functions of short-range wirelesscommunication circuitry 32. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of short-range wirelesscommunication circuitry 329.

FIG. 4—Block Diagram of a Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.4 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2 .

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In suchembodiments, base station 102 may be connected to a legacy evolvedpacket core (EPC) network and/or to a NR core (NRC) network. Inaddition, base station 102 may be considered a 5G NR cell and mayinclude one or more transmission and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTEand UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein, e.g., for defining andusing a resource map for semi-persistent resourcereservations/scheduling for unicast and/or groupcast communications inV2X (vehicle to everything) networks. The processor 404 of the basestation 102 may be configured to implement or support implementation ofpart or all of the methods described herein, e.g., by executing programinstructions stored on a memory medium (e.g., a non-transitorycomputer-readable memory medium). Alternatively, the processor 404 maybe configured as a programmable hardware element, such as an FPGA (FieldProgrammable Gate Array), or as an ASIC (Application Specific IntegratedCircuit), or a combination thereof. Alternatively (or in addition) theprocessor 404 of the BS 102, in conjunction with one or more of theother components 430, 432, 434, 440, 450, 460, 470 may be configured toimplement or support implementation of part or all of the featuresdescribed herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

FIG. 5: Block Diagram of Cellular Communication Circuitry

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some embodiments. It is noted thatthe block diagram of the cellular communication circuitry of FIG. 5 isonly one example of a possible cellular communication circuit. Accordingto embodiments, cellular communication circuitry 330 may be include in acommunication device, such as communication device 106 described above.As noted above, communication device 106 may be a user equipment (UE)device, a mobile device or mobile station, a wireless device or wirelessstation, a desktop computer or computing device, a mobile computingdevice (e.g., a laptop, notebook, or portable computing device), atablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3 ). In some embodiments,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively; directly orindirectly. dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5 , cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some embodiments, receive circuitry 532may be in communication with downlink (DL) front end 550, which mayinclude circuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some embodiments, receive circuitry 542 may be in communicationwith DL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some embodiments, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via modem 510), switch570 may be switched to a first state that allows modem 510 to transmitsignals according to the first RAT (e.g., via a transmit chain thatincludes transmit circuitry 534 and UL front end 572). Similarly, whencellular communication circuitry 330 receives instructions to transmitaccording to the second RAT (e.g., as supported via modem 520), switch570 may be switched to a second state that allows modem 520 to transmitsignals according to the second RAT (e.g., via a transmit chain thatincludes transmit circuitry 544 and UL front end 572).

In some embodiments, the cellular communication circuitry 330 may beconfigured to implement methods for performing network assistedside-link resource configuration for unicast and/or multi-cast/groupcastcommunications in V2X (vehicle to everything) networks, e.g., as furtherdescribed herein.

As described herein, the modem 510 may include hardware and softwarecomponents for implementing the above features or for time divisionmultiplexing UL data for NSA NR operations, as well as the various othertechniques described herein. The processors 512 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 512 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 512, in conjunction with one or more of theother components 530, 532, 534, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 512 may include one or moreprocessing elements. Thus, processors 512 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 512. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 512.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for communicating ascheduling profile for power savings to a network, as well as thevarious other techniques described herein. The processors 522 may beconfigured to implement part or all of the features described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a non-transitory computer-readable memory medium). Alternatively (or inaddition), processor 522 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 522, in conjunction with one or more of theother components 540, 542, 544, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 522 may include one or moreprocessing elements. Thus, processors 522 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 522. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 522.

5G NR Architecture with LTE

In some implementations, fifth generation (5G) wireless communicationwill initially be deployed concurrently with current wirelesscommunication standards (e.g., LTE). For example, dual connectivitybetween LTE and 5G new radio (5G NR or NR) has been specified as part ofthe initial deployment of NR. Thus, as illustrated in FIGS. 6A-B,evolved packet core (EPC) network 600 may continue to communicate withcurrent LTE base stations (e.g., eNB 602). In addition, eNB 602 may bein communication with a 5G NR base station (e.g., gNB 604) and may passdata between the EPC network 600 and gNB 604. Thus, EPC network 600 maybe used (or reused) and gNB 604 may serve as extra capacity for UEs,e.g., for providing increased downlink throughput to UEs. In otherwords, LTE may be used for control plane signaling and NR may be usedfor user plane signaling. Thus, LTE may be used to establish connectionsto the network and NR may be used for data services.

FIG. 6B illustrates a proposed protocol stack for eNB 602 and gNB 604.As shown, eNB 602 may include a medium access control (MAC) layer 632that interfaces with radio link control (RLC) layers 622 a-b. RLC layer622 a may also interface with packet data convergence protocol (PDCP)layer 612 a and RLC layer 622 b may interface with PDCP layer 612 b.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 612 a may interface via a master cell group (MCG) bearer toEPC network 600 whereas PDCP layer 612 b may interface via a splitbearer with EPC network 600.

Additionally, as shown, gNB 604 may include a MAC layer 634 thatinterfaces with RLC layers 624 a-b. RLC layer 624 a may interface withPDCP layer 612 b of eNB 602 via an X2 interface for information exchangeand/or coordination (e.g., scheduling of a UE) between eNB 602 and gNB604. In addition, RLC layer 624 b may interface with PDCP layer 614.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 614 may interface with EPC network 600 via a secondary cellgroup (SCG) bearer. Thus, eNB 602 may be considered a master node (MeNB)while gNB 604 may be considered a secondary node (SgNB). In somescenarios, a UE may be required to maintain a connection to both an MeNBand a SgNB. In such scenarios, the MeNB may be used to maintain a radioresource control (RRC) connection to an EPC while the SgNB may be usedfor capacity (e.g., additional downlink and/or uplink throughput).

5G Core Network Architecture—Interworking with Wi-Fi

In some embodiments, the 5G core network (CN) may be accessed via (orthrough) a cellular connection/interface (e.g., via a 3GPP communicationarchitecture/protocol) and a non-cellular connection/interface (e.g., anon-3GPP access architecture/protocol such as Wi-Fi connection). FIG. 7Aillustrates an example of a 5G network architecture that incorporatesboth 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access tothe 5G CN, according to some embodiments. As shown, a user equipmentdevice (e.g., such as UE 106) may access the 5G CN through both a radioaccess network (RAN, e.g., such as gNB or base station 604) and anaccess point, such as AP 112. The AP 112 may include a connection to theInternet 700 as well as a connection to a non-3GPP inter-workingfunction (N3IWF) 702 network entity. The N3IWF may include a connectionto a core access and mobility management function (AMF) 704 of the 5GCN. The AMF 704 may include an instance of a 5G mobility management (5GMM) function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.As shown, the AMF 704 may include one or more functional entitiesassociated with the 5G CN (e.g., network slice selection function (NSSF)720, short message service function (SMSF) 722, application function(AF) 724, unified data management (UDM) 726, policy control function(PCF) 728, and/or authentication server function (AUSF) 730). Note thatthese functional entities may also be supported by a session managementfunction (SMF) 706 a and an SMF 706 b of the 5G CN. The AMF 706 may beconnected to (or in communication with) the SMF 706 a. Further, the gNB604 may in communication with (or connected to) a user plane function(UPF) 708 a that may also be communication with the SMF 706 a.Similarly, the N3IWF 702 may be communicating with a UPF 708 b that mayalso be communicating with the SMF 706 b. Both UPFs may be communicatingwith the data network (e.g., DN 710 a and 710 b) and/or the Internet 700and IMS core network 710.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments. As shown, a userequipment device (e.g., such as UE 106) may access the 5G CN throughboth a radio access network (RAN, e.g., such as gNB or base station 604or eNB or base station 602) and an access point, such as AP 112. The AP112 may include a connection to the Internet 700 as well as a connectionto the N3IWF 702 network entity. The N3IWF may include a connection tothe AMF 704 of the 5G CN. The AMF 704 may include an instance of the 5GMM function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.In addition, the 5G CN may support dual-registration of the UE on both alegacy network (e.g., LTE via base station 602) and a 5G network (e.g.,via base station 604). As shown, the base station 602 may haveconnections to a mobility management entity (MME) 742 and a servinggateway (SGW) 744. The MME 742 may have connections to both the SGW 744and the AMF 704. In addition, the SGW 744 may have connections to boththe SMF 706 a and the UPF 708 a. As shown, the AMF 704 may include oneor more functional entities associated with the 5G CN (e.g., NSSF 720,SMSF 722, AF 724, UDM 726, PCF 728, and/or AUSF 730). Note that UDM 726may also include a home subscriber server (HSS) function and the PCF mayalso include a policy and charging rules function (PCRF). Note furtherthat these functional entities may also be supported by the SMF 706 aand the SMF 706 b of the 5G CN. The AMF 706 may be connected to (or incommunication with) the SMF 706 a. Further, the gNB 604 may incommunication with (or connected to) the UPF 708 a that may also becommunication with the SMF 706 a. Similarly, the N3IWF 702 may becommunicating with a UPF 708 b that may also be communicating with theSMF 706 b. Both UPFs may be communicating with the data network (e.g.,DN 710 a and 710 b) and/or the Internet 700 and IMS core network 710.

Note that in various embodiments, one or more of the above describednetwork entities may be configured to perform methods to implementmechanisms for performing network assisted side-link resourceconfiguration for unicast and/or multi-cast/groupcast communications inV2X (vehicle to everything) networks, e.g., as further described herein.

FIG. 8 illustrates an example of a baseband processor architecture for aUE (e.g., such as UE 106), according to some embodiments. The basebandprocessor architecture 800 described in FIG. 8 may be implemented on oneor more radios (e.g., radios 329 and/or 330 described above) or modems(e.g., modems 510 and/or 520) as described above. As shown, thenon-access stratum (NAS) 810 may include a 5G NAS 820 and a legacy NAS850. The legacy NAS 850 may include a communication connection with alegacy access stratum (AS) 870. The 5G NAS 820 may include communicationconnections with both a 5G AS 840 and a non-3GPP AS 830 and Wi-Fi AS832. The 5G NAS 820 may include functional entities associated with bothaccess stratums. Thus, the 5G NAS 820 may include multiple 5G MMentities 826 and 828 and 5G session management (SM) entities 822 and824. The legacy NAS 850 may include functional entities such as shortmessage service (SMS) entity 852, evolved packet system (EPS) sessionmanagement (ESM) entity 854, session management (SM) entity 856, EPSmobility management (EMM) entity 858, and mobility management (MM)/GPRSmobility management (GMM) entity 860. In addition, the legacy AS 870 mayinclude functional entities such as LTE AS 872, UMTS AS 874, and/orGSM/GPRS AS 876.

Thus, the baseband processor architecture 800 allows for a common 5G-NASfor both 5G cellular and non-cellular (e.g., non-3GPP access). Note thatas shown, the 5G MM may maintain individual connection management andregistration management state machines for each connection.Additionally, a device (e.g., UE 106) may register to a single PLMN(e.g., 5G CN) using 5G cellular access as well as non-cellular access.Further, it may be possible for the device to be in a connected state inone access and an idle state in another access and vice versa. Finally,there may be common 5G-MM procedures (e.g., registration,de-registration, identification, authentication, as so forth) for bothaccesses.

Note that in various embodiments, one or more of the above describedelements may be configured to perform methods to implement mechanismsfor performing network assisted side-link resource configuration forunicast and/or multi-cast/groupcast communications in V2X (vehicle toeverything) networks, e.g., as further described herein.

Network Assisted Side-Link Configuration

In some existing implementations, vehicle-to-everything (V2X)communications, e.g., as specified by 3GPP TS 22.185 V.14.3.0, allowsfor communication between a vehicle (e.g., a mobile unit within avehicle, such as a wireless device comprised within or currentlycontained within a vehicle and/or another transmitter contained orcomprised with a vehicle) and various wireless devices. For example, asillustrated by FIG. 9 , a vehicle, such as vehicle 902 a, maycommunicate with various devices (e.g., devices 902 b-f), such as roadside units (RSUs), infrastructure (V2I), network (V2N), pedestrian(V2P), and/or other vehicles (V2V). In addition, as shown, all deviceswithin the V2X framework may communicate with other devices. V2Xcommunications may utilize both long range (e.g., cellular)communications as well as short to medium range communications (e.g.,non-cellular). In some contemplated implementations, the non-cellularcommunications may use unlicensed bands as well as a dedicated spectrumat 5.9 GHz. Moreover, V2X communications may include unicast,multi-cast, groupcast, and/or broadcast communications. Eachcommunication type may employ an LBT mechanism. Further, under the V2Xcommunication protocol, a transmitter may reserve periodic slots withina reservation period.

In some existing implementations, 5G NR V2X may include variousscheduling modes. For example, 5G NR V2X mode 1 may be designed fornetwork assisted configuration of side-link transmission resources and5G NR V2X mode 2 may be designed for UE self-determination of side-linktransmission resources. However, under existing implementations (e.g.,LTE V2X), there is no specific design for unicast transmissions. Inaddition, unicast transmission may only be visible in upper layers andnot visible (or inviable) in access stratum (AS) layer. In someimplementations, a quality of service (QoS) model may be used forunicast transmissions. In such implementations, a per-packet QoS model,based on PPPP/PPPR (proximity services (ProSe) Per Packet Priority perProSe Per Packet Reliability), may be implemented without a bearer levelor L2 level parameter configuration. Alternatively, 5G NR V2X mode 1 ormode 2 may be used for unicast transmissions. However, 5G NR V2Xrequirements for unicast specific AS configuration exchanges betweendevices (e.g., procedures/configurations for bearer level, handshaking,and so forth), may increase signaling overhead on a link that has lowerquality (reliability) as compared to traditional uplink/downlinkconnections (e.g., via a Uu interface).

Embodiments described herein provide mechanisms for user equipmentdevices (UEs), such as UE 106, in connected mode to leverage networkassistance to perform side-link AS configuration and PC5 connectionsetup and/or PC5 connection release. In some embodiments, relying on thenetwork to configure/release side-link configuration may reducesignaling overhead on the side-link as well as increase reliability ofconfiguration transmissions. Further, in some embodiments, relying onthe network to relay important (e.g., high-priority) side-link data viaUu interface may improve transmission reliability.

In some embodiments, when a UE (such as UE 106) is in a connected mode(e.g., attached to a base station, such as gNB 604), the base stationserving the UE may provide side-link configuration to the UE. In someembodiments, when a UE is not in connected mode (e.g., is in idle modeand/or inactive mode), the UE may initiate a radio resource control(RRC) connection setup procedure to attach to the network prior to thebase station providing side-link configuration to the UE.

In some embodiments, for configuring a side-link unicast link, a basestation may aid a UE in locating a target UE and setup a side-link forthe UE pair. In addition, the base station may provide a side-linkunicast configuration to both UEs. In some embodiments, when a UE entersconnected mode, the UE may report (or indicate) its side-link identifier(SL ID) and/or side-link capability, to the base station. The basestation may store the UE's side-link information as well as share theUE's side-link information with neighboring cells and/or neighboringbase stations.

In some embodiments, when UE requests setup of a side-link unicast link,a base station may assist the UE in finding a target UE using the targetUE's SL ID. In some embodiments, the base station may also use thetarget UE's cell radio network temporary identifier (C-RNTI), cell,and/or base station links to find the target UE. In some embodiments, ifthe target UE is in an idle and/or inactive state, the network may pagethe UE. In some embodiments, if the target UE is in an inactive state,the network may directly page the target UE within the RAN-basednotification area (RNA). In some embodiments, if the target UE is in anidle state, a serving base station may directly page the target UE. Inother words, the network may implement a paging mechanism that may beRAN triggered for idle UEs, e.g., with a paging area that could be thesame and/or different from a core network (CN) paging area. In someembodiments, if the target UE is in an idle state, the base station mayindicate the paging request to an MME/AMF. In some embodiments, the AMFmay trigger the CN paging for side-link (V2X) usage.

In some embodiments, the network may maintain SL UE pair information forUEs that are in connected mode, e.g., via a Uu interface. In someembodiments, in case of side-link failure, the network may assist the UEin recovery of the side-link.

In some embodiments, the network may relay (or forward) side-link datafrom the UE to the targeted UE via a Uu interface. For example, thenetwork may configure the same V2X bearer transmitted via both a Uuinterface and a PC5 interface. In some embodiments, the network mayoperate in any of a duplication mode (same packets transmitted via bothUu and PC5 interfaces), split mode (different packets transmitted viathe Uu interface and the PC5 interface), and/or fallback/switch mode (Uuinterface used as a fallback during failure of side-link).

In some embodiments, a UE, such as UE 106 in connected mode (and/or aspart of an attachment procedure), may provide a serving base station,such as gNB 604, with V2X information, such as a V2X identifier, adestination identifier (e.g., a V2X identifier for a target UE, such asanother UE 106), traffic quality of service (QoS) requirements, and/orPC5 interface capabilities. The service base station (e.g., the network)may then provide, based at least in part on the V2X information providedby the UE, corresponding side-link access stratum (AS) configuration tothe UE. The side-link AS configuration may be applicable to any or allof a unicast, groupcast, and/or broadcast transmission.

In some embodiments, once the serving base station receives the UE's V2Xinformation, the serving base station may store the V2X information,including the UE's V2X identifier. Further, the serving base station mayshare the UE's V2X information amongst neighboring base stations and/orneighboring cells, e.g., to assist in side-link AS configuration forunicast transmissions. For example, when the UE wants to setup aside-link unicast transmission (e.g., a PC5 unicast transmission), theUE may provide a destination V2X identifier (e.g., of a target UE) tothe serving base station. The serving base station may then perform V2XUE pairing according to, and/or based on, a mapping of UE V2Xidentifiers and serving cells/base stations. For example, the basestation may check validity of the UE pair, e.g., the base station mayacquire V2X information associated with the UE pair from the network viaa V2X function and/or the V2X function may aid the base station inacquiring the V2X information associated with the UE pair from thenetwork. Upon validation, the base station may complete the UE pairingif the target UE is in a connected state. Alternatively, uponvalidation, the network may page the target UE if the target UE is notin a connected state. Once the target UE has entered a connected state,the UE pairing may be completed.

In some embodiments, once the UE pairing is successfully completed, thenetwork (e.g., base stations serving the UEs) may store the UE pairinginformation (e.g., V2X identifiers, capabilities, side-linkconfiguration, C-RNTI, serving cell of each UE) and providecorresponding side-link AS configurations to each UE. In someembodiments, if the UE pairing fails, the network (e.g., serving basestation) may indicate the pairing failure to the UE and provide the UEwith pairing failure information. The UE may then indicate the failureto upper layers of the UE. In some embodiments, upon completion of theside-link transmissions, the UE may indicate completion information tothe serving base station and the side-link configuration may be releasedfrom each UE.

FIG. 10 illustrates a block diagram of an example of signaling fornetwork assisted side-link configuration and setup, according to someembodiments. The signaling shown in FIG. 10 may be used in conjunctionwith any of the systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the signaling shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional signaling may also be performed as desired. Asshown, this signaling may proceed as follows.

As shown, a UE 1006, which may be a UE 106 as described above, mayestablish (or have previously established) a radio resource control(RRC) connection 1012 with a gNB 1002, which may be a base station 102and/or a gNB 604 as described above. In other words, UE 1006 may beconnected to (or in a connected state) with gNB 1002. Thus, gNB 1002 maybe considered a serving base station of UE 1006. Further, UE 1006 maysend (or transmit) V2X information 1014 to gNB 1002. In someembodiments, the V2X information may include a destination identifier, aV2X identifier associated with the UE 1006, traffic QoS requirements,traffic QoS pattern, and/or PC5 capabilities. In other words, the UE1006 may request assistance with configuration of a side-link with atarget UE. UE 1006 may receive a PC5 configuration 1016 from gNB 1002.The PC5 configuration 1016 may include any or all of layer 2 (L2)resource block (RB) allocation, L2 configuration, layer 1 (L1)configuration, a transmit/receive pool allocation, and/or an indicationof a network scheduling method. Thereafter, the PC5 link 1018 betweenthe UE and the target UE may be established.

FIG. 11 illustrates a block diagram of another example of signaling fornetwork assisted side-link configuration and setup, according to someembodiments. The signaling shown in FIG. 11 may be used in conjunctionwith any of the systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the signaling shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional signaling may also be performed as desired. Asshown, this signaling may proceed as follows.

As shown, a UE 1106 a, which may be a UE 106 as described above, mayestablish (or have previously established) a radio resource control(RRC) connection 1112 with a gNB 1102 a, which may be a base station 102and/or a gNB 604 as described above. In other words, UE 1106 a may beconnected to (or in a connected state) with gNB 1102 a. Thus, gNB 1102 amay be considered a serving base station of UE 1106 a. In someembodiments, as part of the connection procedure (and/or afterestablishment of the connection), the UE 1106 a may send (ortransmit/share) its V2X identifier, V2X capabilities, and associatedcell information to base station 1106 a.

Similarly, a UE 1106 b, which may be a UE 106 as described above, mayestablish (or have previously established) a radio resource control(RRC) connection 1116 with a gNB 1102 b, which may be a base station 102and/or a gNB 604 as described above. In other words, UE 1106 b may beconnected to (or in a connected state) with gNB 1102 b. Thus, gNB 1102 bmay be considered a serving base station of UE 1106 b. In someembodiments, as part of the connection procedure (and/or afterestablishment of the connection), the UE 1106 b may send (ortransmit/share) its V2X identifier, V2X capabilities, and associatedcell information to gNB 1102 b.

The gNB 1102 a may, after establishing a connection with UE 1106 a, send(or transmit/share) V2X information (e.g., cell and V2X IDs 1114)associated with UE 1106 a to gNB 1102 b as well as the network ingeneral. In some embodiments, the gNB 1102 a may validate and/orauthenticate the V2X information associated with UE 1106 a prior tosharing UE 1106 a's V2X information with the network (e.g., gNB 1102 b).In some embodiments, gNB 1102 a may perform a validity check and/orauthentication based, at least in part, on any, any combination of,and/or all of an operations and management (OAM) channel check, corenetwork (CN) key/authentication management field (AMF) key verification,and/or ProSe Function.

Similarly, gNB 1102 b may, after establishing a connection with UE 1106b, send (or transmit/share) V2X information (e.g., cell and V2X IDs1118) associated with UE 1106 b to gNB 1102 a as well as the network ingeneral. In some embodiments, the gNB 1102 b may validate and/orauthenticate the V2X information associated with UE 1106 b prior tosharing UE 1106 b's V2X information with the network (e.g., gNB 1102 a).In some embodiments, gNB 1102 b may perform a validity check and/orauthentication based, at least in part, on any, any combination of,and/or all of an operations and management (OAM) channel check, corenetwork (CN) key/authentication management field (AMF) key verification,and/or ProSe Function.

UE 1106 a may send (or transmit) V2X information 1120 to gNB 1102 a. Insome embodiments, the V2X information may include a destinationidentifier (e.g., identifying UE 1106 b as a target UE), a V2Xidentifier associated with the UE 1106 a, traffic QoS requirements,traffic QoS pattern, and/or PC5 capabilities. In other words, the UE1106 a may request assistance from gNB 1102 a to configure a side-linkwith UE 1106 b.

The gNB 1102 a may send (or transmit/share) a V2X pair request 1122 withgNB 1102 b. The V2X pair request 1122 may include a side-linkconfiguration as well as the V2X identifier associated with the UE 1106b. The gNB 1102 b may confirm the pairing of UEs 1106 a and 1106 b andmay send (or transmit/share) a V2X pair confirmation 1124 with gNB 1102a.

UE 1106 a may then receive a side-link (e.g., PC5) configuration 1126from gNB 1102 a. The side-link configuration 1126 may include any or allof layer 2 (L2) resource block (RB) allocation, L2 configuration, layer1 (L1) configuration, a transmit/receive pool allocation, and/or anindication of a network scheduling method. Similarly, UE 1106 b mayreceive a side-link (e.g., PC5) configuration 1128 from gNB 1102 b. Theside-link configuration 1128 may include any or all of layer 2 (L2)resource block (RB) allocation, L2 configuration, layer 1 (L1)configuration, a transmit/receive pool allocation, and/or an indicationof a network scheduling method. Thereafter, the PC5 link 11130 betweenthe UE 1106 a and the UE 1106 b may be established and PC5 data 1132 maybe transmitted between the UE pair.

FIG. 12 illustrates a block diagram of another example of signaling fornetwork assisted side-link configuration and setup, according to someembodiments. The signaling shown in FIG. 12 may be used in conjunctionwith any of the systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the signaling shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional signaling may also be performed as desired. Asshown, this signaling may proceed as follows.

As shown, a UE 1206 a, which may be a UE 106 as described above, mayestablish (or have previously established) a radio resource control(RRC) connection 1212 with a gNB 1202 a, which may be a base station 102and/or a gNB 604 as described above. In other words, UE 1206 a may beconnected to (or in a connected state) with gNB 1202 a. Thus, gNB 1202 amay be considered a serving base station of UE 1206 a. In someembodiments, as part of the connection procedure (and/or afterestablishment of the connection), the UE 1206 a may send (ortransmit/share) its V2X identifier, V2X capabilities, and associatedcell information to gNB 1202 a.

The gNB 1202 a may, after establishing a connection with UE 1206 a, send(or transmit/share) V2X information (e.g., cell and V2X IDs 1214)associated with UE 1206 a to gNB 1202 b as well as the network ingeneral. In some embodiments, the gNB 1202 a may validate and/orauthenticate the V2X information associated with UE 1206 a prior tosharing UE 1206 a's V2X information with the network (e.g., gNB 1202 b).In some embodiments, gNB 1202 a may perform a validity check and/orauthentication based, at least in part, on any, any combination of,and/or all of an operations and management (OAM) channel check, corenetwork (CN) key/authentication management field (AMF) key verification,and/or ProSe Function.

UE 1206 a may send (or transmit) V2X information 1216 to gNB 1202 a. Insome embodiments, the V2X information may include a destinationidentifier (e.g., identifying UE 1206 b as a target UE), a V2Xidentifier associated with the UE 1206 a, traffic QoS requirements,traffic QoS pattern, and/or PC5 capabilities. In other words, the UE1206 a may request assistance from gNB 1202 a to configure a side-linkwith UE 1206 b.

The gNB 1202 a may send (or transmit/share) a V2X pair request 1218 withgNB 1202 b. The V2X pair request 1218 may include a side-linkconfiguration as well as the V2X identifier associated with the UE 1206b. The gNB 1202 b may determine that UE 1206 b is not in a connectedstate. In response, the gNB 1202 b may broadcast V2X paging 1220requesting UE 1206 b establish a connection with gNB 1202 b. In someembodiments, if UE 1206 b is in an inactive state, the gNB 1202 b maydirectly page UE 1206 b within the RAN-based notification area (RNA). Insome embodiments, if UE 1206 b is in an idle state, gNB 1202 b maydirectly page UE 1206 b. In other words, the network may implement apaging mechanism that may be RAN triggered for idle UEs, e.g., with apaging area that could be the same and/or different from a core network(CN) paging area. In some embodiments, if UE 1206 b is in an idle state,the gNB 1202 b may indicate the paging request to an MME/AMF. In someembodiments, the AMF may trigger the CN paging for side-link (V2X)usage.

Upon receiving the V2X paging 1220, UE 1206 b, which may be a UE 106 asdescribed above, may establish (and/or resume) a radio resource control(RRC) connection 1222 with gNB 1202 b, which may be a base station 102and/or a gNB 604 as described above. In other words, UE 1206 b may entera connected state with gNB 1202 b. Thus, gNB 1202 b may become a servingbase station of UE 1206 b. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1206 b may send (or transmit/share) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1206 b.

After establishing a connection with UE 1206 b, the gNB 1202 b mayvalidate and/or authenticate the V2X information associated with UE 1206b prior to sharing UE 1206 b's V2X information with the network (e.g.,gNB 1202 a). In some embodiments, gNB 1202 b may perform a validitycheck and/or authentication based, at least in part, on any, anycombination of, and/or all of an operations and management (OAM) channelcheck, core network (CN) key/authentication management field (AMF) keyverification, and/or ProSe Function.

In addition, after establishing the connection with UE 1206 b and/orafter validating and/or authenticating the V2X information associatedwith UE 1206 b, gNB 1202 b may confirm the pairing of UEs 1206 a and1206 b and may send (or transmit/share) a V2X pair confirmation 1224with gNB 1202 a.

UE 1206 a may then receive a side-link (e.g., PC5) configuration 1226from gNB 1202 a. The side-link configuration 1226 may include any or allof layer 2 (L2) resource block (RB) allocation, L2 configuration, layer1 (L1) configuration, a transmit/receive pool allocation, and/or anindication of a network scheduling method. Similarly, UE 1206 b mayreceive a side-link (e.g., PC5) configuration 1228 from gNB 1202 b. Theside-link configuration 1228 may include any or all of layer 2 (L2)resource block (RB) allocation, L2 configuration, layer 1 (L1)configuration, a transmit/receive pool allocation, and/or an indicationof a network scheduling method. Thereafter, the PC5 link 12130 betweenthe UE 1206 a and the UE 1206 b may be established and PC5 data 1232 maybe transmitted between the UE pair.

FIG. 13 illustrates a block diagram of an example of signaling forrelease of a network assisted side-link transmission configuration,according to some embodiments. The signaling shown in FIG. 13 may beused in conjunction with any of the systems or devices shown in theabove Figures, among other devices. In various embodiments, some of thesignaling shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional signaling may also be performed asdesired. As shown, this signaling may proceed as follows.

As shown, a UE 1306 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1312 with a gNB 1302 a, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1306 a may be connected to (or ina connected state) with gNB 1302 a. Thus, gNB 1302 a may be considered aserving base station of UE 1306 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1306 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1302 a.

Similarly, a UE 1306 b, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1314 with a gNB 1302 b, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1306 b may be connected to (or ina connected state) with gNB 1302 b. Thus, gNB 1302 b may be considered aserving base station of UE 1306 b. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1306 b may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1302 b.

The UEs 1306 a and 1306 b may be performing a PC5 data transmission1316, e.g., established as described above. Upon completion of the PC5data transmission 1316, UE 1306 a may send (or transmit/share) V2Xinformation 1318 to gNB 1302 a. In some embodiments, the V2X informationmay include a destination identifier (e.g., identifying UE 1306 b as atarget UE), a V2X identifier associated with the UE 1306 a, and anindication to discontinue a V2X configuration with a target UE. In otherwords, the UE 1306 a may request assistance from gNB 1302 a to terminate(or discontinue/release) a side-link with UE 1306 b.

The gNB 1302 a may send (or transmit/share) a V2X pair release 1320 withgNB 1302 b. The V2X pair release 1320 may include and/or identify UE1306 b. Upon receiving the V2X pair release 1320, gNB 1302 b may confirmthe release (or termination) of the V2X session and send (ortransmit/share) a V2X pair release confirmation 1322 with gNB 1302 a.Subsequently, gNB 1302 a may send (or transmit/share) a side-linkrelease 1324 with UE 1306 a. The side-link release 1324 may releaseside-link resources assigned to UE 1306 a for the PC5 data transmission1316. Similarly, gNB 1302 b may send (or transmit/share) a side-linkrelease 1326 with UE 1306 b. The side-link release 1326 may releaseside-link resources assigned to UE 1306 b for the PC5 data transmission1316.

FIG. 14 illustrates a block diagram of an example of signaling for UEhandover during a network assisted side-link transmission, according tosome embodiments. The signaling shown in FIG. 14 may be used inconjunction with any of the systems or devices shown in the aboveFigures, among other devices. In various embodiments, some of thesignaling shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional signaling may also be performed asdesired. As shown, this signaling may proceed as follows.

As shown, a UE 1406 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1412 with a gNB 1402 a, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1406 a may be connected to (or ina connected state) with gNB 1402 a. Thus, gNB 1402 a may be considered aserving base station of UE 1406 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1406 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1402 a.

Similarly, a UE 1406 b, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1414 with a gNB 1402 b, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1406 b may be connected to (or ina connected state) with gNB 1402 b. Thus, gNB 1402 b may be considered aserving base station of UE 1406 b. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1406 b may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1402 b.

The UEs 1406 a and 1406 b may be performing a PC5 data transmission1416, e.g., established as described above. During the transmission, oneof the gNBs 1402 a and/or 1402 b may detect a handover condition for oneof the UEs 1406 a and/or 1406 b. For example, gNB 1402 a may detect ahandover condition and share/update location information (e.g., V2Xidentifiers, base station information, cell information) via a handoverexchange 1418 with gNB 1402 b. In addition, gNB 1402 a may send ahandover command 1420 to UE 1402 a. The handover command 1420 mayinclude an indication for UE 1402 a to continue the PC5 datatransmission in an exceptional pool (e.g., PC5 data transmission 1422)during the handover procedure. Upon completion of the handover, UE 1402a may establish an RRC connection 1424 with gNB 1402 b. In someembodiments, as part of the connection procedure (and/or afterestablishment of the connection), the UE 1406 a may have sent (ortransmitted/shared) its V2X identifier, V2X capabilities, and associatedcell information to gNB 1402 b. Further, after completion of thehandover, the PC5 data transmission may resume in a transmit pool (e.g.,PC5 data transmission 1426.

FIG. 15 illustrates a block diagram of an example of signaling for UEre-establishment after a radio link failure during a network assistedside-link transmission, according to some embodiments. The signalingshown in FIG. 15 may be used in conjunction with any of the systems ordevices shown in the above Figures, among other devices. In variousembodiments, some of the signaling shown may be performed concurrently,in a different order than shown, or may be omitted. Additional signalingmay also be performed as desired. As shown, this signaling may proceedas follows.

As shown, a UE 1506 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1512 with a gNB 1502 a, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1506 a may be connected to (or ina connected state) with gNB 1502 a. Thus, gNB 1502 a may be considered aserving base station of UE 1506 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1506 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1502 a.

Similarly, a UE 1506 b, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1515 with a gNB 1502 b, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1506 b may be connected to (or ina connected state) with gNB 1502 b. Thus, gNB 1502 b may be considered aserving base station of UE 1506 b. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1506 b may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1502 b.

The UEs 1506 a and 1506 b may be performing a PC5 data transmission1516, e.g., established as described above. During the transmission, oneof the UEs 1506 a and/or 1506 b may experience a radio link failure(RLF). For example, UE 1506 a may experience an RLF 1518 and initiate are-establishment procedure (e.g., via re-establishment request 1520)with gNB 1502 b. In some embodiments, during the re-establishmentprocedure, UE 1502 a may continue with the PC5 data transmission in anexceptional pool (e.g., PC5 data transmission 1522). Further, gNBs 1502a and 1502 b may update location information associated with UE 1506 a(e.g., via UE context fetch 1524). The updated location information mayinclude V2X identifiers, base station information, and/or cellinformation. Further, as part of the UE context fetch 1524, gNB 1502 bmay determine a V2X configuration based on the updated locationinformation of the UE, e.g., via a handover command. The gNB 1502 b mayadditionally initiate a re-establishment/re-configuration procedure(e.g., re-configuration 1526) with UE 1502 a. There-establishment/re-configuration procedure may include an updated (ornew) side-link configuration based on the updated location informationof UE 1502 a. Upon completion of the re-establishment procedure, UE 1502a may establish an RRC connection with gNB 1502 b. In some embodiments,as part of the connection procedure (and/or after establishment of theconnection), the UE 1506 a may have sent (or transmitted/shared) its V2Xidentifier, V2X capabilities, and associated cell information to gNB1502 b. Further, after completion of the handover, the PC5 datatransmission may resume in a transmit pool (e.g., PC5 data transmission1528.

FIG. 16 illustrates a block diagram of an example of signaling for UEre-establishment failure after a radio link failure during a networkassisted side-link transmission, according to some embodiments. Thesignaling shown in FIG. 16 may be used in conjunction with any of thesystems or devices shown in the above Figures, among other devices. Invarious embodiments, some of the signaling shown may be performedconcurrently, in a different order than shown, or may be omitted.Additional signaling may also be performed as desired. As shown, thissignaling may proceed as follows.

As shown, a UE 1606 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1612 with a gNB 1602 a, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1606 a may be connected to (or ina connected state) with gNB 1602 a. Thus, gNB 1602 a may be considered aserving base station of UE 1606 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1606 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1602 a.

Similarly, a UE 1606 b, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1616 with a gNB 1602 b, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1606 b may be connected to (or ina connected state) with gNB 1602 b. Thus, gNB 1602 b may be considered aserving base station of UE 1606 b. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1606 b may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1602 b.

The UEs 1606 a and 1606 b may be performing a PC5 data transmission1616, e.g., established as described above. During the transmission, oneof the UEs 1606 a and/or 1606 b may experience a radio link failure(RLF). For example, UE 1606 a may experience an RLF 1618 and initiate are-establishment procedure (e.g., via re-establishment request 1620)with gNB 1602 b. In some embodiments, during the re-establishmentprocedure, UE 1602 a may continue with the PC5 data transmission in anexceptional pool (e.g., PC5 data transmission 1622). In someembodiments, the re-establishment procedure may not be successful (e.g.,may fail). Thus, gNB 1602 b may send an RRC release command 1624 to UE1606 a. The RRC release command 1624 may clear (delete) the V2Xconfiguration and indicate that UE 1606 a enter an idle state. Further,gNB 1602 b may send an RRC re-configuration command 1626 to UE 1606 b,including release (e.g., clearing and/or deleting) of the V2Xconfiguration. In some embodiments, the release of the V2X configurationmay proceed similarly to release of other UE access stratumconfigurations.

FIG. 17 illustrates a block diagram of an example of signaling fornetwork assisted side-link configuration and setup failure, according tosome embodiments. The signaling shown in FIG. 17 may be used inconjunction with any of the systems or devices shown in the aboveFigures, among other devices. In various embodiments, some of thesignaling shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional signaling may also be performed asdesired. As shown, this signaling may proceed as follows.

As shown, a UE 1706, which may be a UE 106 as described above, mayestablish (or have previously established) a radio resource control(RRC) connection 1712 with a gNB 1702, which may be a base station 102and/or a gNB 604 as described above. In other words, UE 1706 may beconnected to (or in a connected state) with gNB 1702. Thus, gNB 1702 maybe considered a serving base station of UE 1706. Further, UE 1706 maysend (or transmit) V2X information 1714 to gNB 1702. In someembodiments, the V2X information may include a destination identifier, aV2X identifier associated with the UE 1706, traffic QoS requirements,traffic QoS pattern, and/or PC5 capabilities. In other words, the UE1706 may request assistance with configuration of a side-link with atarget UE. In some embodiments, if gNB 1702 cannot identify and/orlocate the target UE, e.g., based on the provided destinationidentifier, the gNB 1702 may send a side-link configuration failuremessage 1716 to UE 1706. Thus, the PC5 link may fail at 1718 and theside-link may not be established with the target UE. In someembodiments, the UE 1706 may report the side-link failure to upperlayers of the UE 1706.

FIG. 18 illustrates a block diagram of an example of signaling fornetwork assisted recovery from a side-link failure, according to someembodiments. The signaling shown in FIG. 18 may be used in conjunctionwith any of the systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the signaling shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional signaling may also be performed as desired. Asshown, this signaling may proceed as follows.

As shown, a UE 1806, which may be a UE 106 as described above, may havepreviously established a radio resource control (RRC) connection 1812with a gNB 1802, which may be a base station 102 and/or a gNB 604 asdescribed above. In other words, UE 1806 may be connected to (or in aconnected state) with gNB 1802. Thus, gNB 1802 may be considered aserving base station of UE 1806. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1806 may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1802.

The UE 1806 may have PC5 data link 1814 for transmitting data to apaired UE. During the transmission, UE 1806 may experience a failure ofthe PC5 link (e.g., PC5 link failure 1816). For example, if radioconditions worsen, the UE 1806 may suspend PC5 transmissions/receptionsand may fall back to Uu interface with gNB 1802. In response, the UE1806 may send (or transmit) side-link failure information 1818 to gNB1802. In some embodiments, the side-link failure information may includea failure cause and corresponding measurement results. In someembodiments, if the UE 1806 does not have a connection with gNB 1802(and/or has lost connection), the UE 1806 may re-establish a connectionwith gNB 1802 prior to sending the side-link failure information 1818.

Upon receipt of the side-link failure information 1818, the gNB 1802 mayrelease and/or re-configure the side-link configuration and resource tothe UE 1806 and the paired UE. For example, the gNB 1802 may send theside-link reconfiguration 1820 to UE 1806. In some embodiments, if thepaired UEs belong to different gNBs and the network maintains the V2X UEpair (e.g., via re-configuration), then the gNB 1802 may coordinate withthe gNB serving the paired UE on the side-link re-configuration.

FIG. 19 illustrates a block diagram of an example of signaling fornetwork assisted side-link data transmission, according to someembodiments. The signaling shown in FIG. 19 may be used in conjunctionwith any of the systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the signaling shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional signaling may also be performed as desired. Asshown, this signaling may proceed as follows.

As shown, a UE 1906 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection1912 with a gNB 1902, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 1906 a may be connected to (or ina connected state) with gNB 1902. Thus, gNB 1902 may be considered aserving base station of UE 1906 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 1906 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 1902.

The UE 1906 a may have a side-link established with UE 1906 b and may betransmitting side-link data 1914 to UE 1906 b. In some embodiments, theUE 1906 a may maintain both a PC5 link with UE 1906 b and a UU link withgNB 1902 for a V2X service transmission that may have been configured bythe network, e.g., as described above. Thus, UE 1906 a may betransmitting the side-link data to gNB 1902 via data transmission 1916.In some embodiments, the UE 1906 a may establish a V2X bearer with asplit and/or duplicated model. In some embodiments, the V2X bearer maybe anchored at a packet data convergence protocol (PDCP) layer of aprotocol stack implemented on UE 1906 a. In some embodiments, the V2Xbearer may be anchored at a service data adaptation protocol (SDAP)layer of a protocol stack implemented on the UE 1906 a. Thus, the UE1906 a may transmit the side-link data via multiple links. In someembodiments, the UE 1906 a may transmit the same packet on both links(e.g., duplication mode). In some embodiments, the UE 1906 a maytransmit on the PC5 link and only switch to the Uu link if channelconditions worsen. As shown, the gNB 1902 may receive the side-link dataand relay (e.g., at 1918) the side-link to UE 1906 b via datatransmission 1920. In some embodiments, UE 1906 b may receive theside-link data via both the PC5 link and the Uu link.

FIG. 20 illustrates a block diagram of an example of signaling fornetwork assisted side-link data transmission with SDAP duplication,according to some embodiments. The signaling shown in FIG. 20 may beused in conjunction with any of the systems or devices shown in theabove Figures, among other devices. In various embodiments, some of thesignaling shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional signaling may also be performed asdesired. As shown, this signaling may proceed as follows.

As shown, a UE 2006 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection2012 with a gNB 2002, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 2006 a may be connected to (or ina connected state) with gNB 2002. Thus, gNB 2002 may be considered aserving base station of UE 2006 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 2006 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 2002.

In some embodiments, a protocol stack may be implemented on and/or by UE2006 a. As shown, the protocol stack may include an application layer2036 a, a V2X layer 2046 a, and an SDAP layer 2056 a. The SDAP layer2056 a may anchor both a PC5 link with UE 2006 b and a Uu link with gNB2002. Lower layers may be split between the PC5 link and the Uu link.Thus, lower layers may include PDCP layers 2066 a and 2068 a, RLC layers2076 a and 2078 a, MAC layers 2086 a and 2088 a, and/or L1 layers 2096 aand 2098 a.

As noted, the UE 2006 a may have a side-link (PC5 link) established withUE 2006 b and may be transmitting side-link data 2014 to UE 2006 b. UE2006 b may also implement a protocol stack similar to UE 2006 a. Thus,the protocol stack may include an application layer 2036 b, a V2X layer2046 b, and an SDAP layer 2056 b. The SDAP layer 2056 b may anchor botha PC5 link with UE 2006 a and a Uu link with gNB 2002. Lower layers maybe split between the PC5 link and the Uu link. Thus, lower layers mayinclude PDCP layers 2066 b and 2068 b, RLC layers 2076 b and 2078 b, MAClayers 2086 b and 2088 b, and/or L1 layers 2096 b and 2098 b. Inaddition, gNB 2002 may also implement a split protocol stack that mayinclude an SDAP layer 2052. The SDAP layer 2052 may anchor both a Uulink with UE 2006 a and a Uu link with UE 2006 b. Lower layers may besplit between the Uu links. Thus, lower layers may include PDCP layers2062 a and 2062 b, RLC layers 2072 a and 2072 b, MAC layers 2082 a and2082 b, and/or L1 layers 2092 a and 2092 b.

As shown, side-link data 2014 may be received at SDAP layer 2056 a fromupper layers and SDAP layer 2056 a may add a sequence number (SN) toeach SDAP service data unit (SDU) used to transmit data. The side-linkdata 2014 may pass through the lower layers of UE 2006 a and eventuallybe received at PCDP layer 2066 b of UE 2006 b and passed on to SDAPlayer 2056 b of UE 2006 b. Similarly, transmitted data 2016 may passthrough the lower layers of UE 2006 a and eventually be received at PCDPlayer 2062 a and passed on to SDAP layer 2052 of gNB 2002. SDAP layer2052 may forward (e.g., at 2018) the received data to PDCP layer 2062 bfor transmission to UE 2006 b via PDCP layer 2066 b. In someembodiments, both data transmissions may be received at the SDAP layer2056 b. SDAP layer 2056 b may perform duplication detection based on theSN and may discard duplicated packets prior to forwarding the data on tohigher layers.

FIG. 21 illustrates a block diagram of an example of signaling fornetwork assisted side-link data transmission with PDCP duplication,according to some embodiments. The signaling shown in FIG. 21 may beused in conjunction with any of the systems or devices shown in theabove Figures, among other devices. In various embodiments, some of thesignaling shown may be performed concurrently, in a different order thanshown, or may be omitted. Additional signaling may also be performed asdesired. As shown, this signaling may proceed as follows.

As shown, a UE 2106 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection2112 with a gNB 2102, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 2106 a may be connected to (or ina connected state) with gNB 2102. Thus, gNB 2102 may be considered aserving base station of UE 2106 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 2106 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 2102.

In some embodiments, a protocol stack may be implemented on and/or by UE2106 a. As shown, the protocol stack may include an application layer2136 a, a V2X layer 2146 a, an SDAP layer 2156 a, and a PDCP layer 2166a. The PDCP layer 2156 a may anchor both a PC5 link with UE 2106 b and aUu link with gNB 2102. Lower layers may be split between the PC5 linkand the Uu link. Thus, lower layers may include RLC layers 2176 a and2178 a, MAC layers 2186 a and 2188 a, and/or L1 layers 2196 a and 2198a.

As noted, the UE 2106 a may have a side-link (PC5 link) established withUE 2106 b and may be transmitting side-link data 2114 to UE 2106 b. UE2106 b may also implement a protocol stack similar to UE 2106 a. Thus,the protocol stack may include an application layer 2136 b, a V2X layer2146 b, an SDAP layer 2156 b, and a PDCP layer 2166 b. The PDCP layer2166 b may anchor both a PC5 link with UE 2106 a and a Uu link with gNB2102. Lower layers may be split between the PC5 link and the Uu link.Thus, lower layers may include RLC layers 2176 b and 2178 b, MAC layers2186 b and 2188 b, and/or L1 layers 2196 b and 2198 b. In addition, gNB2102 may also implement a split protocol stack that may include an SDAPlayer 2152 and a PDCP layer 2162. The PDCP layer 2162 may anchor both aUu link with UE 2106 a and a Uu link with UE 2106 b. Lower layers may besplit between the Uu links. Thus, lower layers may include RLC layers2172 a and 2172 b, MAC layers 2182 a and 2182 b, and/or L1 layers 2192 aand 2192 b.

As shown, side-link data 2114 may be received at PDCP layer 2166 a fromupper layers and PDCP layer 2166 a may apply a security key and add asequence number (SN) to each PDCP packet data unit (SDU) used totransmit data. The side-link data 2114 may pass through the lower layersof UE 2106 a and eventually be received at PCDP layer 2166 of UE 2106 b.Similarly, transmitted data 2116 may have the same security key appliedand pass through the lower layers of UE 2106 a and eventually bereceived at PCDP layer 2162 and passed on to PDCP layer 2162 of gNB2102. PDCP layer 2162 may forward (e.g., at 2118) the received data fortransmission to UE 2106 b via PDCP layer 2166 b. In some embodiments,both data transmissions may be received at the PDCP layer 2166 b. PDCPlayer 2166 b may perform duplication detection based on the SN and maydiscard duplicated packets prior to forwarding the data on to higherlayers.

FIG. 22 illustrates a block diagram of another example of signaling fornetwork assisted side-link data transmission, according to someembodiments. The signaling shown in FIG. 22 may be used in conjunctionwith any of the systems or devices shown in the above Figures, amongother devices. In various embodiments, some of the signaling shown maybe performed concurrently, in a different order than shown, or may beomitted. Additional signaling may also be performed as desired. Asshown, this signaling may proceed as follows.

As shown, a UE 2206 a, which may be a UE 106 as described above, mayhave previously established a radio resource control (RRC) connection2212 with a gNB 2202, which may be a base station 102 and/or a gNB 604as described above. In other words, UE 2206 a may be connected to (or ina connected state) with gNB 2202. Thus, gNB 2202 may be considered aserving base station of UE 2206 a. In some embodiments, as part of theconnection procedure (and/or after establishment of the connection), theUE 2206 a may have sent (or transmitted/shared) its V2X identifier, V2Xcapabilities, and associated cell information to gNB 2202.

The UE 2206 a may have a side-link established with UE 2206 b and may betransmitting side-link data 2214 to UE 2206 b. In some embodiments, theUE 2206 a may maintain both a PC5 link with UE 2206 b and a UU link withgNB 2202 for a V2X service transmission that may have been configured bythe network, e.g., as described above. Thus, upon detecting a side-linkfailure 2216, the UE 2206 a may transmit the side-link data to gNB 2202via data transmission 2218, e.g., as a fallback to the PC5 link. In someembodiments, the UE 2206 a may establish a V2X bearer with a splitand/or duplicated model. In some embodiments, the V2X bearer may beanchored at a PDCP layer or an SDAP layer of a protocol stackimplemented on UE 2206 a. Thus, the UE 2206 a may transmit the side-linkdata via multiple links. As shown, the gNB 2202 may receive theside-link data and relay (e.g., at 2220) the side-link to UE 2206 b viadata transmission 2222.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of a methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE 106 or BS 102) may beconfigured to include a processor (or a set of processors) and a memorymedium, where the memory medium stores program instructions, where theprocessor is configured to read and execute the program instructionsfrom the memory medium, where the program instructions are executable toimplement any of the various method embodiments described herein (or,any combination of the method embodiments described herein, or, anysubset of any of the method embodiments described herein, or, anycombination of such subsets). The device may be realized in any ofvarious forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A user equipment device (UE), comprising: atleast one antenna; at least one radio, wherein the at least one radio isconfigured to perform cellular communication using at least one radioaccess technology (RAT); and one or more processors coupled to the atleast one radio, wherein the one or more processors and the at least oneradio are configured to perform communications; and wherein the one ormore processors are configured to cause the UE to: establish a radioresource control (RRC) connection with a first base station; perform PC5data transmissions with an other UE, wherein the other UE has an RRCconnection with a second base station; receive, during the PC5 datatransmissions, a handover command from the first base station, whereinthe handover command includes an indication to continue the PC5 datatransmissions in an exceptional pool during a handover procedure to thesecond base station; and establish an RRC connection with the secondbase station as part of the handover procedure.
 2. The UE of claim 1,wherein the one or more processors are further configured to cause theUE to: resume, after completion of the handover procedure, the PC5 datatransmissions with the other UE in a transmit pool.
 3. The UE of claim1, wherein, to establish the RRC connection with the first base station,the one or more processors are further configured to cause the UE to:share, with the first base station, a vehicle-to-everything (V2X)identifier, V2X capabilities of the UE, and associated cell information.4. The UE of claim 3, wherein the one or more processors are furtherconfigured to cause the UE to: receive, from the base station, aside-link configuration for PC5 data transmissions with the other UE. 5.The UE of claim 4, wherein the side-link configuration includes aresource allocation defined in time and frequency.
 6. The UE of claim 5,wherein the side-link configuration further includes at least one of:layer two resource blocks; or a layer one configuration.
 7. The UE ofclaim 5, wherein the resource allocation specifies a transmit/receivepool of resource blocks defined in time and frequency.
 8. The UE ofclaim 1, wherein, to establish the RRC connection with the second basestation, the one or more processors are further configured to cause theUE to: share, with the first base station, a vehicle-to-everything (V2X)identifier, V2X capabilities of the UE, and associated cell information.9. A base station, comprising: at least one antenna; at least one radio,wherein the at least one radio is configured to perform cellularcommunication using at least one radio access technology (RAT); and oneor more processors coupled to the at least one radio, wherein the one ormore processors and the at least one radio are configured to performcommunications; and wherein the one or more processors are configured tocause the base station to: establish radio resource control (RRC)connection with a first user equipment (UE); detect, during PC5 datatransmissions between the first UE and a second UE, a handover conditionassociated with the first UE; and transmit, during the PC5 datatransmissions, a handover command to the first UE, wherein the handovercommand includes an indication to continue the PC5 data transmissions inan exceptional pool during a handover procedure to an other basestation, and wherein the second UE has an RRC connection to the otherbase station.
 10. The base station of claim 9, wherein the one or moreprocessors are further configured to cause the base station to: sharelocation information associated with the first UE with the other basestation.
 11. The base station of claim 10, wherein the locationinformation includes a vehicle-to-everything (V2X) identifier of thefirst UE, V2X capabilities of the first UE, and cell information. 12.The base station of claim 9, wherein, to establish the RRC connectionwith the first UE, the one or more processors are further configured tocause the base station to: receive, from the first UE, avehicle-to-everything (V2X) identifier, V2X capabilities of the firstUE, and associated cell information; and transmit, to the first UE, aside-link configuration for PC5 data transmissions with the second UE,wherein the side-link configuration includes a resource allocationdefined in time and frequency.
 13. The base station of claim 12, whereinthe side-link configuration further includes at least one of: layer tworesource blocks; or a layer one configuration.
 14. The base station ofclaim 12, wherein the resource allocation specifies a transmit/receivepool of resource blocks defined in time and frequency.
 15. A method foruser equipment (UE) handover during a network assisted side-linktransmission, comprising: a base station establishing radio resourcecontrol (RRC) connection with a first user equipment (UE); detecting,during PC5 data transmissions between the first UE and a second UE, ahandover condition associated with the first UE; and transmitting,during the PC5 data transmissions, a handover command to the first UE,wherein the handover command includes an indication to continue the PC5data transmissions in an exceptional pool during a handover procedure toan other base station, and wherein the second UE has an RRC connectionto the other base station.
 16. The method of claim 15, furthercomprising: the base station, sharing location information associatedwith the first UE with the other base station.
 17. The method of claim16, wherein the location information includes a vehicle-to-everything(V2X) identifier of the first UE, V2X capabilities of the first UE, andcell information.
 18. The method of claim 15, wherein establishing theRRC connection with the first comprises receiving, from the first UE, avehicle-to-everything (V2X) identifier, V2X capabilities of the UE, andassociated cell information.
 19. The method of claim 18, furthercomprising: the base station, transmitting, to the first UE, a side-linkconfiguration for PC5 data transmissions with the second UE.
 20. Themethod of claim 19, wherein the side-link configuration further includesat least one of: layer two resource blocks; or a layer oneconfiguration.